System and Method for Partner Key Management

ABSTRACT

A system and method for implementing an interoperable credential management protocol for processing online transactions. The protocol, referred to as the Partner Key Management (PKM) protocol provides an improved alternative to traditional public key infrastructure (PKI), particularly for use in high-value commercial transactions which require additional controls on the use of credentials for authentication and authorization. According to the PKM protocol, a user may take advantage of credential interoperability by using the same credential at a plurality of different financial institutions for authentication or digital signatures. Additionally, the credential interoperability achieved according to the PKM protocol allows the user to employ the same credential at a plurality of financial institutions for the purpose of digital or electronic signatures.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No. 61/221,540, titled “System and Method for Partner Key Management”, filed on Jun. 29, 2009. U.S. Provisional Application No. 61/221,540 is hereby incorporated by reference herein.

FIELD OF THE INVENTION

The present invention relates generally to payment processing and management, and, more particularly, to a system and method for administering and managing a vendor and buyer invoicing and payment process in a vendor contract compliant manner.

BACKGROUND OF THE INVENTION

Public Key Infrastructure (PKI) is a set of hardware, software, people, policies, and procedures needed to create, manage, distribute, use, store, and revoke digital certificates. In cryptography, a PKI is an arrangement that binds public keys with respective user identities by means of a certificate authority (CA). In a PKI arrangement, the user identity must be unique within each CA domain. The binding is established through the registration and issuance process, which, depending on the level of assurance the binding has, may be carried out by software at a CA, or under human supervision. The PKI role that assures this binding is called the Registration Authority (RA). For each user, the user identity, the public key, their binding, validity conditions and other attributes are made unforgeable in public key certificates issued by the CA.

Although useful in certain contexts, the Public Key Infrastructure (PKI) has an inherent liability shortcoming that prohibits widespread adoption of inter-financial institution interoperability, especially in connection with high monetary value transactions/payments. Although existing security frameworks may satisfy the requirements associated with small monetary value transactions/payments, wholesale banking requires a framework capable of meeting the security requirements associated with value-bearing transactions of US$500,000,000 and beyond.

Most conventional PKT-based systems are adapted to deploy certificates to computers as opposed to people. Some PKI systems have had success deploying SSL certificates onto web servers. Although SSL certificate technology allows for deployment to individual users, market penetration for personal certificates is limited due to a number of reasons. For example, in the cases where an end-user obtains a personal certificate, inter-organizational interoperability is severely restricted.

One primary reason for this restriction is a lack of a viable liability model which addresses security requirements established, among many various factors, by a financial institution's regulatory, contractual, and technical environments. It is well-established that financial institutions are subject to an array of regulatory, contractual, and business requirements to effectively identify individuals who engage in business with the financial institution. Banking operations are subject to a multitude of regulations, including technical audit requirements designed to protect the safety and soundness of the financial institution's electronic operations. Among these regulatory requirements are standards governing the processes to set up credentials for a financial institution's customers. In the United States, banking regulators generally publish regulatory guidelines which, in effect, establish technical and other requirements for regulated financial institutions, including processes governing systems for the electronic transmission of value bearing instructions.

If a registration authority contractually agrees to issue credentials used by other legal entities, then the registration authority typically seeks to limit its liability contractually. The economic reality of registration authorities servicing wholesale funds transfers is that most registration authorities could not or would not honor the levels of liability experienced for a faulty acceptance (e.g., transfers of hundreds of millions or billions of dollars), leaving the financial institution as the de facto liable party. In view of this potential liability, wholesale financial institutions typically opt to accept payment instructions for which it has absolute certainty of the identity and legitimacy of the individual transmitting the instructions. If a financial institution were to accept a credential issued by another party in an interoperable PKI model, the financial institution would need to trust absolutely the other party's connection between the credential and the referenced identity.

However, no financial institution or other registration authority could or would accept unlimited liability for all transactions/payments executed at a different financial institution. As an illustration, the top wire processor in terms of dollar volume is JPMorgan Chase Treasury Services, which processes more than $3 Trillion dollars in some single days. No third party financial institution or registration authority would be in a position to accept liability for JPMorgan's payment processes; conversely, JPMorgan would in turn not wish to accept liability for other financial institutions' payments.

Traditional PKI credentials, while interoperable in theory, alone are insufficient to overcome the following primary obstacles inherent to the use of interoperable credentials in high-value transactions:

1. Autonomy: If, for example, a bank (Second Bank) is contemplating recognizing credentials issued by another bank (First Bank), Second Bank would understandably want to audit First Bank's practices as a credential issuer against Second Bank's policies. Understandably, First Bank would be reluctant to agree to audits of its operations by competitors such as Second Bank.

2. Liability: Non-bank issuers of PM credentials neither want, nor are in a position to accept, liability for failed high-value transactions. One way of addressing this problem is for a financial institution to issue its own credentials to limit risk and to recognize only the credentials it issues; however, this solution is not interoperable by definition.

3. Expense: If commercial financial institutions were to recognize non-bank certificate issuers for high-value commercial transactions, then commercial financial institutions would need to be connected to the non-financial institution certificate issuers. This is an added operational expense for financial institutions, creating a further barrier to achieving interoperability.

Authorizing online high-value commercial transactions requires a higher level of diligence when compared to consumer or retail transactions. A single high-value transaction may involve the transfer of hundreds of millions of dollars. The inherent risk associated with wholesale online banking compels many financial institutions to require additional security beyond authenticating users at login time. Additional security often takes the form of tighter controls and limits on the use of credentials. Ultimately, each financial institution trusts itself more than any other entity. This naturally leads to the practice of financial institutions issuing their own credentials.

Historically, a cash manager of a corporation would hold separate credentials from each financial institution with which he or she deals. While this satisfies the needs of commercial financial institutions, the corporation is forced to simultaneously hold accounts in multiple financial institutions, the insistence upon and proliferation of unique credentials is viewed by customers as poor service. Hence, it is increasingly important for global financial services providers to offer credentials that: (1) are interoperable to provide customer convenience, and (2) meet the needs of high-value commercial transactions in terms of authentication, authorization, and liability.

Therefore, there is a need in the art for an interoperable credential management system and method for online transactions, particularly high-value commercial transactions.

SUMMARY OF THE INVENTION

The present application describes embodiments of a system, method and computer readable medium which provides an improved alternative to the traditional PKI by providing a unique approach to the management of certificates and other credentials which allows for interoperability amongst different financial institutions or other parties. The system, method, and computer readable medium employ a certificate management model, herein referred to as a “Partner Key Management (PKM)” protocol or model that advantageously provides for interoperability amongst third parties and multiple independent (non-affiliated) financial institutions based on credentials such as asymmetric cryptography and certificates. According to embodiments of the present invention, the PKM model provides for an interoperable methodology wherein a user (on behalf of an associated corporation) may securely engage in a computer-based or online transaction with a bank or other financial institution. The PKM protocol focuses on authorization to use a credential.

According to embodiments of the present invention, a user (e.g., a cash manager or other individual associated with a corporation) obtains a credential from a credential distributor (i.e., any entity capable of providing credentials to a user and/or a corporation for use in the transmission, execution, and/or engagement in an online transaction via a computer network). According to embodiments of the present invention, the user may employ a single credential with multiple financial institutions without first arranging for the plurality of financial institutions to mutually agree upon a global credential policy and/or a common credential provider.

After obtaining the credential, the user submits a request to each of his or her financial institutions for permission to use the credential in connection with future transactions with the respective financial institutions. In response to the request, the financial institution confirms the identity of the user and examines the credential, in accordance with the financial institution's security standards. If the financial institution accepts the credential, the financial institution authorizes the credential to represent the user. According to an embodiment of the present invention, the user may register the same credential (i.e., request and receive authorization from a financial institution for the credential to represent the user for use with multiple financial institutions to achieve interoperability.

According to embodiments of the present invention, the authorization process may vary between the financial institutions, with each financial institution setting its own operational policy governing the conditions in which the financial institution accepts the credentials based upon the financial institution's published operating rules. In this regard, the PKM program employs machine-readable policy statements which define and detail a participating financial institution's policy, rules, parameters, and/or requirements for accepting, processing, and managing transaction requests.

The machine-readable policy statement (e.g., a XML document), herein referred to as manifest of credential usage (MOCU), is an agreement between a third party sender (e.g., a corporation) and a bank which defines the rules, regulations, security provisions, conditions, requirements, and/or framework governing the manner in which transactions will be handled between the third party sender and the financial institution. The MOCU comprises information governing the corporation-financial institution relationship as it relates to online transactions, such as, for example, the type of permissible credential media, a list of approved credential providers, a revocation definition, a timestamp definition, a signature policy, and requirements concerning credential technology.

According to embodiments of the present invention, the PKM protocol provides a solution to the liability concerns which traditionally prohibited widespread interoperability amongst non-affiliated financial institutions. By addressing the interoperability issue, the PKM protocol establishes a “shared investment” model for subsidizing the token technology which is amortized across all of the financial institutions participating in/utilizing the PKM platform, without imposing a “shared” liability amongst the participants.

In addition, the PKM protocol allows each participating financial institution to deploy a single technology solution/implementation that handles multiple “islands of interoperability”, wherein each island of interoperability is defined as a collection of entities that all operate in accordance with the same MOCU. This single-implementation approach allows the financial institutions the ability to adapt to and grow into new markets that have unique operating rules. In addition, the financial institution gains the advantage of not needing to deploy new software and hardware for each island, particularly multi-national financial institutions that manage transactions involving multi-national corporations wherein each country may have its own unique security infrastructure.

Furthermore, the system and method according to embodiments of the present invention provide for a shared cost model which amortizes the cost of the credentials amongst the participating financial institutions. Advantageously, participation by a plurality of financial institutions results in a per-user cost of a single credential that is lower than the per-user cost of multiple credentials in accordance with the conventional PKI framework.

According to embodiments of the present invention, an interoperable certificate management protocol referred to as the “partner key management” (PKM) protocol is described in detail. The PKM framework is configured to allow for the interoperability of credentials in the execution of high-value or other transactions.

According to embodiments of the present invention, a user may take advantage of credential interoperability by using the same credential at a plurality of different financial institutions for authentication or digital signatures. As used herein, the term “authentication” is intended to include, but is not limited to, the act of verifying the identity of a user, and is generally designed to protect against fraudulent logon activity. See, “2002 CISA Review Manual”, Information Systems Audit and Control Association, ISBN: 1-893209-20-2. p. 399. Electronic authentication (E-authentication) is the process of establishing confidence in user identities electronically presented to an information system. See, Burr, William, E. et al., “Electronic Authentication Guideline”, NIST 800-63. As used herein, the term “digital signature” is intended to include, but is not limited to, a piece of information, in a digitized form of a signature that provides sender authenticity (i.e., authenticates the sender), message integrity and non-repudiation. 2002 CISA Review Manual, p. 404. Non-repudiation is a service which prevents an entity from denying previous commitments or actions. When disputes arise due to an entity denying that certain actions were taken, a means to resolve the situation is necessary. For example, one entity may authorize the purchase of property by another entity and later deny such authorization was granted.” See, Menezes, Alfred J. et al. “Handbook of Applied Cryptography”, CRC Press LLC, Boca. Raton 1997, ISBN: 0-8493-8523-7 p 4. One having ordinary skill in the art will appreciate that an authentication mechanism is not required to provide non-repudiation. The term “message integrity” refers to a means by which a recipient receives a message from a sender; and checks to ensure that the message was received in its entirety and without modification by an unauthorized third party.

When a user engages in an authentication process, the financial institution needs the user to prove his or her claimed identity. The user presents an authentication credential as a means of providing evidence of the user's claimed identity. Credential interoperability allows the user to employ the same authentication credential at a plurality of financial institutions. Credential interoperability may also allow the user to employ the same credential at a plurality of financial institutions for the purpose of digital or electronic signatures.

The PKM protocol imposes few restrictions on which credential provider (or certification authority) may be used in connection with the PKM system and reinterprets the authority of credentials in a constrained and controlled manner. In this regard, the third party sender/user may independently select a credential provider, without permission or approval from the financial institution with which the third party sender/user wishes to engage with in a transaction. In addition, the PKM protocol supports a general validation model, including a user validation model (also referred to as a sender validation model), which in conjunction with the reinterpretation of authority, scales better, provides interoperability, and reduces the cost for the relying party (e.g., the financial institution).

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more readily understood from the detailed description of exemplary embodiments presented below considered in conjunction with the attached drawings, of which:

FIG. 1 illustrates an exemplary process according to the PKM model, in accordance with an embodiment of the present invention;

FIG. 2 is an exemplary system configured to implement e PKM protocol, according to an embodiment of the present invention;

FIG. 2A is a flowchart illustrating an exemplary approach to validation in accordance with one embodiment of the invention;

FIG. 3 illustrates an exemplary interoperable credential registration process, according to an embodiment of the present invention;

FIG. 4A is a flowchart illustrating a further approach to validation in accordance with an embodiment of the invention;

FIGS. 4 and 5 present a process flow (FIG. 4) and a schematic depiction (FIG. 5) of an exemplary processing of an online transaction according to the PKM protocol, according to an embodiment of the present invention; and

FIG. 6 illustrates an exemplary process flow of the PKM protocol, according to an embodiment of the present invention.

It is to be understood that the attached drawings are for purposes of illustrating the concepts of the invention and may not be to scale.

DETAILED DESCRIPTION OF THE INVENTION

The present invention relates to a system, method, and computer readable medium for employing a certificate management model, referred to as the “Partner Key Management (PKM)” protocol. The PKM protocol provides an improved framework for the processing of online transactions between an entity which desires to engage in online transactions (e.g., a corporation, organization, individual, etc.), referred to herein as a “corporation”, communicatively connected to an institution (e.g., a financial institution, a healthcare institution, etc.), referred to herein as a “financial institution” or “institution”, via a network using interoperable credentials. As used herein, the term “credential” is intended to include, but is not limited to, an object that authoritatively binds an identity (and optionally, additional attributes) to a token possessed and controlled by a person”. See, NIST 800-63. As used herein, the term “authentication credential” is intended to include, but is not limited to, an electronic system that authoritatively binds an identity (and optionally, additional attributes) to a token possessed and controlled by a person or machine.

As used herein, the term “interoperable credential” is intended to include, but is not limited to, a single credential designed to provide security which is accepted by a plurality of different institutions (e.g., independent, non-affiliated entities) pursuant to the PKM protocol. As used herein, the term “communicatively connected” is intended to include any type of connection, whether wired or wireless, in which data may be communicated between one or more computers. The term “communicatively connected” is intended to include a connection between devices and/or programs within a single computer or between devices and/or programs on separate computers. The term “computer” is intended to include any data processing device, such as a desktop computer, a laptop computer, a mainframe computer, a personal digital assistant, a server, a handheld device, or any other device able to process data. Although the present application describes the PKM protocol primarily in the context of the management of financial-based transactions, one having ordinary skill in the art will appreciate that the PKM protocol may be used for securing any type of transaction, particularly those including sensitive data, such as, for example, a health care related transaction over a health care network.

According to an embodiment of the present invention, the third party sender, herein referred to as the “corporation”, utilizes a Third Party Sender/User Module 20 to engage in an online transaction (i.e., any transaction executed via a computer network) via the network 30 with a “participating” institution (i.e., any institution utilizing the PKM protocol to facilitate online transactions with one or more third party senders) by communicating with the financial institution PKM module (first institution 40A, second institution 40B) using the interoperable credential. The Financial Institutions PKM Module 40A, 40B is computer-implemented module or agent configured to enable the Financial Institution to participate in the PKM protocol, as detailed in the embodiments described below.

The Third Party Sender/User Module 20 and Financial institution PKM Module 40A, 40B may respectively include any combination of systems and sub-systems such as electronic devices including, but not limited to, computers, servers, databases, or the like. The electronic devices may include any combination of hardware components such as processors, databases, storage drives, registers, cache, random access memory (RAM) chips, data buses, or the like and/or software components such as operating systems, database management applications, or the like.

The Third Party Sender/User Module 20 and Financial. Institutions PKM Module 40A, 40B may respectively comprise one or more computing devices. The computing device(s) may have one or more processors, storage (e.g., storage devices, memory, etc.), and software modules. The computing device(s), including its processor(s), storage, and software modules, may be used in the performance of the techniques and operations described herein.

FIG. 2 illustrates an exemplary process flow in accordance with embodiments of the present invention. With reference to FIGS. 1 and 2, in step 1, a user (i.e., an individual operating on behalf of or under the control of the third party sender/corporation), utilizes the third party sender/user Module 20 to request a credential from a Credential Provider 10.

In step 1, in response to the request, the Credential Provider 10 provides the ‘secure’ credential to the third party sender/user Module 20 (according to the security definition/requirements established by the user or user's company together with the Credential Provider). For example, a first Credential Provider 10 may only distribute credentials (e.g., certificates) on secured USB devices. A user may also obtain software to create self-signed certificates, and thereby create his or her own certificates implying that the user and the second Credential Provider are the same. Advantageously, according to embodiments of the present invention, the PKM protocol supports a general validation model, wherein each third party sender/user Module 20 need only communicate with the Credential Provider or providers 10 to which the third party sender/user Module 20 subscribes. In this regard, in the PKM framework, the institution PKM Module 40 does not need to interact directly with the Credential Provider 10, except optionally for credential validation in the receiver validation model, described in detailed below. Advantageously, the third party sender/user may independently select a Credential Provider 10 with which it subscribes, without being limited to a credential provider which is has been previously approved by the financial institution.

In step 2, after obtaining a credential, the third party sender/user Module 20 submits a request to each of his or her financial institution. PKM modules 40A and 40B to register the credential (i.e., allow for use of the credential to secure future online transactions). According to an embodiment of the present invention, in this step, the financial institution PKM modules 40A and 40B securely assures itself of the user's true identity and examines the credential to determine if the credential meets the financial institution's security standards. For example, some financial institutions may prohibit credentials other than private keys that reside in a secured hardware token.

In step 3, if the financial institution PKM modules 40A and 40B accepts the credential, then the Financial Institution PKM modules 40A and 40B authorizes the credential to represent the user, thereby registering the association between the third party sender/user and the credential. The financial institution PKM modules 40A and 40B stores a record of the authorization/registration in a database 42A, 42B associated therewith. Optionally, the Financial Institution PKM modules 40A and 40B may further communicate with the Credential Provider 10 using the receiver validation model as an aspect of the validation provided by the Validator Module 44A and 44B. In this regard, the financial institution queries to determine if the Credential Provider 10 believes the credential to be currently valid.”

Advantageously, the user may use the same credential with multiple financial institutions by appropriately registering the credential with the respective institutions, thereby generating an interoperable credential. One having ordinary skill in the art will appreciate that the authentication and authorization processes may vary between the financial institutions, wherein each institution may have its own operational policy governing the conditions in which it accepts the credential based upon the financial institution's published operating rules.

The interoperable credential provides flexibility and convenience to the user/third party sender, while permitting the financial institution the ability to implement and follow their own procedure for accepting the credentials and allowing users to employ those credentials. The result is an infrastructure that allows the possibility of interoperability without mandating interoperability. Under the PKM protocol, two financial institutions may independently agree to accept a single credential under their own respective terms, thereby resulting in a credential that is interoperable between the user and each of the said institutions. Advantageously, no financial institution needs to rely upon any other financial institution or external credential provider. No two financial institutions need to communicate.

FIG. 3 illustrates an exemplary implementation of the credential registration process described above in connection with FIGS. 1 and 2. In the example, Alice is a Cash Manager (i.e., the user) employed by Widget Corporation the third party sender). Widget Corporation typically performs its banking operations with two banks: First Hypothetical Bank and Second Hypothetical Bank. Both banks define their respective individual security and financial practices in a proposed agreement with Widget Corporation. Although these standards are not identical to one another, the corporate Treasurer of Widget finds both agreements to be acceptable.

As cash manager, Alice sends a request to a credential provider (labeled as “Credential Provider” in FIG. 3) to obtain a credential. The Credential Provider authorizes authentication credential distribution and provides Alice with key pair authorization, as shown in step SI in FIG. 3. Next, Alice contacts First and Second Hypothetical Bank with the intention of registering the credential, as shown in steps S2 and S3. The two banks have the freedom to require any registration processes that they desire without concerning themselves with mutual consistency. For example. First Hypothetical Bank may require security administrators representing Widget Corporation to sign forms associating Alice with her certificate obtained from the Credential Provider. No requirement exists for Second Hypothetical Bank to implement this same registration process. In the PKM model, a financial institution may also serve as the credential provider. In Step S4 the user signs a transaction (e.g., request for money transfer) using the credential. Advantageously, those skilled in the art will note that the user may repeat Step S4 on a plurality of instances potentially signing a different transaction on each instant.

In the example, the corporate Treasurer at Widget Corporation gains the advantage of utilizing existing processes and security requirements in obtaining credentials. Furthermore, the user, Alice, may register the credentials with multiple financial institutions (e.g., First Hypothetical Bank and Second Hypothetical Bank) to establish interoperable credentials. Advantageously, under the PKM model, Alice only needs to manage a single interoperable credential, as opposed to two non-interoperable credentials (i.e., one for each bank). From the perspective of First Hypothetical Bank and Second Hypothetical Bank, the PKM model did not impose any liability terms which would be unacceptable to their corporate or legal teams. According to an embodiment of the present invention, First and Second Hypothetical Banks may share the cost of obtaining the credential under a shared cost model.

According to embodiments of the present invention, institutions financial institutions, health care institutions, etc.) participating in the PKM program publish an XML document called the Manifest of Credential Usage (MOCU). For example, the MOCU may be written using an XML schema). The MOCU defines how a third party sender (i.e., the corporation) and a financial institution agree to work together, as governed by their mutually agreed upon security procedures. The third party sender and the financial institution have the freedom to establish any suitable rules, processes, standards, procedures, conditions, etc. upon which the two parties mutually agree, provided that the rules, processes, standards, procedures, conditions, etc. are supportable using programming logic.

According to embodiments of the present invention, the MOCU may include any suitable information that establishes the operating security procedures/processes, including, but not limited to, one or a combination of the following types of information:

1) a credential media definition which defines the type of media (e.g., a smart card, USB token, HSM, F1PS-140-2, or a software credential) that is acceptable for use in connection with a transaction under the MOCU;

2) a list of one or more approved credential providers (e.g., third party trusted providers, self-signed certificates, the corporation's infrastructure, and the financial institution's infrastructure) to which the third party sender and the financial institution mutually subscribe;

3) a credential technology definition which sets forth the type of technology required for the credential to be acceptable, such as, for example, a requirement that the certificate supports the X.509 standard. One having ordinary skill in the art will appreciate that the MOCU may specify other suitable technologies, such as, for example, the portable security transaction protocol (PSTP) (see, G. Benson, “Portable Security Transaction Protocol”, Comput. Netw., 51(3):751-766, 2007) which can create signatures using different kinds of credentials, e.g., one-time password, credit card numbers, IP addresses, or machine fingerprints.

4) a timestamp definition setting forth the timestamp rules and the timestamp provider, if any. Optionally, the timestamp definition may specify a real-time threshold value. Generally, the recipient must ensure that it receives and validates a signature before the threshold time limit after the timestamp. For example, a six hour threshold value means that the recipient must validate a signature before six hours expires after the timestamp.

5) a signature policy specifying the number of signatures required for a specific type of transaction, and the roles of signatories. For example, the signature policy may require both an individual signature and a corporate “system” signature in order to consider either signature as valid.

6) a revocation definition describing the type of permissible credential revocation mechanism. e.g., certificate revocation list (CRL), online certificate status protocol (OCSP) (see, M. Myers et al., “X.509 Internet Public Key Infrastructure Online Certificate Status Protocol—OCSP”, RFC 2560 (Proposed Standard), June 1999), etc. The revocation definition also describes the party responsible for enforcing credential revocation; and it describes any specific usage practice. For example, the revocation mechanism may mandate that the recipient of a signature validate a CRL signed by a particular party.

The security requirements mutually agreed to by the financial institution and the corporation are reflected in a specific MOCU, or possibly a list of MOCUs. The security requirements may mandate that the user and/or corporation must attach the MOCU on each signed transaction in order to consider any signature valid. In some embodiments of the present invention multiple MOCUs are attached.

It is to be appreciated by one having ordinary skill in the art that other information may be included in the MOCU to establish the security requirements mutually agreed to by the sender and the financial institution. According to an embodiment of the present invention, the security requirements may mandate that the sender (i.e., the corporation) attach the MOCU to each signed transaction in order for the signature to be valid.

According to an embodiment of the present invention, the PKM protocol enables each participating institution to avoid liability relating to transactions executed by another participating bank within the PKM framework, while allowing for credential interoperability.

As shown in FIG. 1, the Financial Institution PKM Module 40A, 40B comprises a Validator Module 44 (identified in FIG. 1 as Validator Module 44A for Financial Institution PKM Module of the First Institution 40A; and Validator Module 44B for Financial Institution PKM Module of the First institution 40B), a computer module configured to implement a validation model selected by the financial institution. Exemplary approaches to validation which may be implemented by the financial institutions are described herein in connection with steps 4 and 4 a-4 c of FIG. 2A. One having ordinary skill in the art will appreciate that validation by the financial institution is an optional step and may be performed in accordance with the exemplary approaches identified in steps 4 a-4 c, or in accordance with another suitable validation approach.

One exemplary Validator Module 44A, 44B, for use in connection with the present invention is an XML schema validator and general-purpose parser. According to embodiments of the present invention, each participating financial institution may select any of the following three exemplary revocation models, or, alternatively, build its own variant model, for use in accordance with the PKM protocol of the present application, as illustrated in FIG. 2A:

1) Receiver validation (step 4 a): The receiver validation model is typically used in a PKI model. With reference to the previously described example, under a receiver validation model, Alice (i.e., the user) submits a signed transaction the financial institution. Upon receipt, the financial institution validates Alice's signature against a CRL or OCSP responder managed by the certificate provider.

2) Sender validation without evidence (step 4 b): In a sender validation without evidence model, Alice submits a signed transaction to the financial institution, but the financial institution performs no revocation check. The corporation (i.e., Alice's employer) and the financial institution manage Alice's credential using a mechanism external to the signed transaction. For example, a user at Alice's employer is given access to the approver Module 25. When the Approver Module 25 decides that he or she wants to disable Alice's credential, the Approver accesses the Approver Module 25 in order to execute the unapprove step. The Approver Module 25 contacts each Financial Institution PKM Module 40A and 40B independently. The Approver Module 25 instructs each Financial Institution PKM Module 40A and 40B to stop accepting Alice's credential. Upon receipt of the un-approve instruction from an authorized user, the financial institution stops accepting Alice's credential. Please note, that the person who approves the initial setup of Alice's credential at Financial Institution PKM Module 40A and 40B need not be the same person who un-approvers. Furthermore, the same Approver Module 25 may be used in both the Approve and Un-approve steps, or alternatively, they may use different modules. Under this revocation model, if Alice proves to be an untrustworthy individual, then the approver/un-approver may reserve the right to disable Alice's credential. For example, if Alice has a gambling problem, then authorized representatives of Alice's company may contact each of its financial institutions with the instruction to deny Alice's credential. Another example which also results in credential disabling is one where Alice contacts each financial institution because she suspects that her own credential has been compromised (i.e., lost or stolen).

3) Sender validation with evidence (step 4 c): In a sender validation with evidence model, Alice submits her certificate to an OCSP responder, and obtains a response signed by the OCSP responder. Next, Alice signs the transaction and the OCSP response, and then submits the signed transaction and signed OCSP response to the financial institution. The financial institution validates both Alice's signature and the OCSP responder's signature. If the financial institution finds no error, then the financial institution accepts and executes the requested transaction.

In another embodiment of the present invention, Alice sends a CRL as opposed to an OCSP response. That is, Alice submits the signed transaction and signed CRL to the financial institution. The signed CRL is signed by the Credential Provider 10 or the credential provider's authorized representative and indicates that Alice's certificate has not been revoked.

One having ordinary skill in the art will appreciate that multiple financial institutions may all accept the same credential from Alice, while requiring/implementing different revocation models.

An OCSP responder, or a certificate revocation list, is merely revocation mechanisms optimized for scalability. As opposed to requiring the Alice's corporation to contact each of its financial institutions, an OCSP responder or CRL provides a centralized repository which handles certificate revocation. One advantage of the OCSP responder or certificate revocation list is its scalability. For example, if Alice were authorized to engage in transactions on accounts at hundreds or thousands of financial institutions, then the sender validation without evidence model would not be preferred because the sender would need to contact too many financial institutions. However, in practice, corporations tend to contact each of their financial institutions whenever a user's credential changes status because the corporations do not have accounts at too many financial institutions. Even if the financial institution happens to use the traditional receiver validation model, the corporations often contact the financial institutions anyway. So, in financial services, the advantage of receiver validation is relatively small. Frequently, some financial institutions require immediate notification of such status changes. Practically, is in the corporation's best interest to directly contact the financial institutions if the corporation ceases to trust Alice to authorize high-value transactions.

Advantage of sender validation is that it better handles expense and time to market Suppose, for example, a corporation agrees to the services of a new credential provider. Credential interoperability encourages a dynamic market by allowing the corporation the freedom to choose any acceptable credential provider. In the receiver validation model, the corporation could not use that credential with its financial institution until the financial institution agrees to build an online connection to the credential distributor's OCSP responder or certificate revocation list. According to a user validation model (also referred to as a sender validation model), on the other hand, the sender (i.e., the user/corporation) may immediately use the credential with the financial institution without waiting for the costly and possibly slow technology development process.

According to an embodiment of the present invention, the signature used in connection with a transaction includes the MOCU and transaction parameters such as, for example, relevant account numbers, a monetary amount, and recipient/beneficiary information. As shown in FIGS. 1 and 5, the Validator Module 44A, 44B is configured to check each incoming MOCU against the rules specified by the financial institution and the third party sender. The agreed upon rules may be manifested in a list of acceptable MOCUs, referred to as the acceptance list, which is stored in the database 42A, 42B associated with the Validator Module 44A, 44B.

Advantageously, according to an embodiment of the present invention, the financial institution may implement a new policy by adding a new MOCU to its acceptance list. In this regard, the financial institution may adopt any number of MOCUs for use by the financial institution under the PKM program, and may efficiently add new policies without deploying new software.

When the financial institution receives a signed transaction from a third party sender/user Module 20, the financial institution PKM Module 40A, 40B looks up the MOCU covered by the signature associated with the requested transaction against the list of the allowable MOCUs maintained in the financial institution's database 42A, 42B. According to an embodiment of the present invention, the financial institution's system may include hardware and/or software configured to process MOCUs When the financial institution receives a signature, the Validator Module 44 executes the required cryptography and then submits the signature to the MOCU processor for MOCU processing. The financial institution's hardware/software architecture exhibits a high degree of agility because it may be configurable thereby avoiding programming logic changes upon each policy change.

An embodiment of the present invention is described in connection with FIGS. 4A, 4 and 5, by illustrating details of sender validation with evidence 4C of FIG. 2A. As illustrated in FIGS. 4A, 4 and 5, a user (Alice) wishes to make a transaction with a financial institution (referred to as the “bank” in the Figures). To initiate the process, in step A, Alice utilizes a Corporation/User Module 20 to execute a personal signature using her credential over the transaction request and a MOCU. Next, in step B, Alice sends the signed transaction request to a Validator Module 440. In step C, the Validator Module 440 checks for revocation, and obtains a digitally signed revocation statement (i.e., a signed CRL or OCSP response) from a CRL or OCSP responder, as shown in FIG. 5. In step D, the Validator Module 440 provides all of the collected information to a Corporation Module 200. The Corporation Module 200 counter-signs Alice's signed transaction, the signed revocation statement, a timestamp, and the Validator Module's 440 MOCU. Next, the information is sent through the Network 30 to the Financial Institution PKM Module 40, 40A. Next, in step E, the Financial Institution PKM Module 40,40A validates all of its incoming information including both MOCUs, and if compliant, processes the requested transaction. According to embodiments of the present invention, the Central Validator Module 440 may reside in the same entity as the Corporation/User Module 20. In this embodiment of the present invention, individual users execute signatures, but the signature is not valid unless countersigned by the Central Corporation Module 200. The Central Corporation Module 200 does not produce this signature unless directed by the Central Validator Module 440. The Central Validator Module 440 does not authorize the counter signature unless the central valuator module first validated the user's signature, MOCU, revocation information, and any other relevant corporate policy. Each Corporation/User Module 20 and each Central Corporation Module 00 may sign their own MOCUs which need not be the same. However, the Validator Module 44,44A at the financial institution 40A will not accept a signature unless both MOCUs are in accordance with expectations.

According to embodiments of the present invention, the validator Module 44A or 44B described in connection with FIGS. 4 and 5 may be controlled, operated, and managed by a trusted third party, or the financial institution (i.e., the bank). The Central Validator Module 440 may be controlled by a trusted third party or preferably, the user/sender or corporation (i.e., a user/sender validation model).

The sender validation with evidence model ensures proper security provided that both the corporation and the bank trust the signature of the revocation point. However, if the revocation point's credential were revoked, then both the validator and the bank have the responsibility to detect the revocation event of the revocation point (e.g., the provider of the CRL or the operator of the OCSP responder). The corporation and the bank may agree to whom to assign liability in the case where a Central Validator Module 440 improperly checks for revocation before directing a countersignature.

One advantage of the sender validation without evidence model 4 b and the sender validation with evidence model 4 c is that they improve the bank's agility. The bank merely needs to validate the MOCUs without building a connection to every revocation point. The corporate is happy because the banks do not refuse credential providers or charge an extra fee for special-purpose connection points. The banks are happy because they may immediately serve more customers at a low marginal cost.

According to an alternative embodiment of the present invention is described in connection with FIGS. 1 and 6, a user and an Approver Module 25 (also referred to generally as an “approver”) represent a corporation. Via the Corporation/User Module 20, the Corporation/User Module 20 obtains a credential from a Credential Provider 10, in step I. In step II, based on a request from the user, the Financial Institution PKM Module 40A, 40B registers the credential. In step III, the Corporation/User Module 20 provides information concerning the credential to the Approver Module 25. The Approver Module 25 may be configured to consider any suitable information (e.g., user name, user position within corporation, user authority level, nature of transactions engaged in using the credential, etc.) and apply any suitable rules to determine whether or not to approve use of the credential by the user. According to an exemplary embodiment of the present invention, the Approver Module 25 may apply rules and conditions established by the corporation in making the approval/denial decision. Based on the information provided by the Corporation/User Module 20 regarding the credential, the Approver Module 25 determines whether to approve the user's use of the credential. Next, in step IV, assuming approval by the Approver Module 25, the Financial Institution PKM Module 40A, 40B receives approval of the credential from the Approver Module 25. After successfully completing step IV, the Financial Institution PKM Module 40A, 40B allows the Corporation/User Module 20 to use the credential for authentication and digital signatures, when applicable, in step V.

According to an embodiment of the present invention in step II the user or other representative signs the submitted request and a MOCU in accordance to the means and variants described herein.

According to an embodiment of the present invention in step III the approver module signs the submitted request and a MOCU in accordance to the means and variants described herein.

According to an alternative embodiment of the present invention, the order of step II and step III described in connection with FIG. 4 is reversed. As such, the Corporation/User Module 20 sends information concerning the credential to the Approver Module 25 prior to registration of the credentials with the Financial Institution PKM Module 40A, 40B.

According to an embodiment of the present invention, in addition to registering the credential with a first financial institution according to the embodiments described above, the Corporation/User Module 20 (i.e., under the control/direction of the user or other representative of the corporation) sends a request for registration of the credentials to one or more other financial institutions (i.e., the credential is registered with a plurality of financial institutions) according to the steps described above in connection with FIG. 6, thereby resulting in an interoperable credential. The process for registering the credentials with the plurality of financial institutions may be implemented as shown in FIG. 6 (i.e., steps I-IV) or the alternative embodiment wherein step IV is performed prior to the performance of step III. With reference to FIG. 1, the plurality of financial institutions (via the Financial Institution PKM Module 40A, 40B), having registered the credentials, may further communicate with the Credential Provider 10 when using the receiver validation module to obtain a CRL or interact with an OCSP responder.

According to an embodiment of the present invention the means by which the Credential Provider 10 provides revocation information is neither a CRL nor an OCSP responder, but a different means of providing revocation information.

According to an embodiment of the present invention the party that provides revocation information is not the Credential Provider 10, but a different party authorized to provide revocation information.

According to an embodiment of the present invention, the corporation may create its own certificates, thereby omitting the need for a separate Credential Provider 10 from the process/system. With reference to FIG. 6, in this embodiment, the credential registration process comprises steps I, II, III, and IV (as described above), wherein step I is completely executed by the corporation (i.e., the corporation creates its own credentials and provides the credentials to its users). In another embodiment, in the registration step (step I), the user creates a self-signed certificate on his or her computer workstation without needing to communicate with other computers/machines, even within his or her own corporation. According to this embodiment the Corporation/User Module 20 and Credential Provider 10 are the same entity/computer.

According to an embodiment of the present invention, the Corporation/User Module 20 is communicatively connected to a plurality of Approver Modules 25. In this embodiment, the Corporation/User Module 20 and the plurality of Approver Modules 25 are managed by or otherwise represent a corporation. With reference to FIG. 6, the registration process comprising steps 1-V is modified such that in step 111, the user provides information concerning the credential to the plurality of Approver Modules 25. In step V, the Financial Institution PKM Module 40A, 40B requires receipt of approval of the credential from all of the Approver Modules 25 before allowing the user to use the credential for authentication and digital signatures, when applicable. Put another way, the Financial Institution PKM Module 40A, 40B does not permit use of the credential until all required Approver Modules 25 (i.e., the plurality of approvers) submits their respective approvals.

In accordance to an embodiment of the invention the Financial Institution PKM Module 40A, 40B applies a specific rule for the required approvers which may be more than one approver, but less than all approvers, e.g., 3 of 5 approvers. In accordance to an embodiment of the invention approvers may have different approval roles, and the policy requires multiple approvers representing each role.

One having ordinary skill in the state of the art will appreciate that the Approver Module 25 may comprise a specific individual (i.e., an individual computer) or be comprised of a group of individuals (i.e., a group of individual computers). According to an embodiment of the present invention, any member of the authorized approver group or role may submit the approval to the Financial Institution PKM Module 40A, 40B,

In a further embodiment of the invention, no individuals or groups are required for the approval. In this embodiment, the Financial Institution PKM Module 40A, 40B permits use of the credential following satisfaction of steps I and II.

In a further embodiment of the invention, different financial institutions impose different registration rules. For example, one financial institution may require two approval groups prior to authorizing a credential, while another financial institution may require one approver, and still another financial institution may require no approvers. Advantageously, in this embodiment of the PKM protocol, the financial institutions may configure their respective Financial Institution PKM Modules 40A, 40B to implement the financial institution's desired approval configuration. In yet another example, one Financial Institution PKM Module (i.e., Financial Institution PKM Module 40A) may require one sequence of steps ordering (e.g., a sequence of steps I, II, III, IV, V in FIG. 6), while another Financial Institution PKM Module (i.e. Financial Institution PKM Module 40B) may call for a different sequence of steps (e.g., a sequence of steps I, III, II, IV, and V).

In one embodiment of the invention, the registration process allows a plurality of users to share the same credential.

In one embodiment of the invention, the credential is a digital certificate. The user may have private keying material that the user keeps on local storage media to be connected to his or her computer. In one embodiment of the present invention the certificate is signed by the Credential Provider 10 or a suitable certificate authority, known to those having ordinary skill in the art. In one embodiment of the present invention, a certificate path leads up to a root certificate signed by the Credential Provider 10. In one embodiment of the invention, the certificate is self-signed. In yet another embodiment of the present invention, the certificate not signed.

In an alternative embodiment of the present invention, the credential is an IP address and digital signatures are created using PSTP (Portable Security Transaction Protocol). In this embodiment, after the Financial Institution PKM Module 40A, 40B accepts the IP Address (i.e., the credential) for use, the Financial institution PKM Module 40A, 40B prohibits electronic interaction with the user unless the user connects to the financial institution from the registered IP address. In one embodiment of the invention, the user registers a range or plurality of IP addresses. After the Financial institution PKM Module 40A, 40B accepts the range of IP addresses for use, the Financial Institution PKM Module 40A, 40B prohibits electronic interaction with the user unless the user connects from an IP address within the registered range. In one embodiment of the invention, the user registers a collection of ranges of IP addresses. After the Financial Institution PKM Module 40A, 40B accepts the collection of ranges of IP addresses for use, the Financial Institution PKM Module 40A, 40B prohibits electronic interaction with the user unless the user connects from an IP address within the one of the registered range. In one embodiment of the invention, the user registers computer addresses using some format other than IP addresses, e.g., MAC address.

According to an embodiment of the present invention, the invention, the credential is a one-time password and digital signatures are created using PSTP, as described in detail in U.S. Publication No. 2005/0091492, titled “Portable Security Transaction Protocol” by G. Benson et al., the entirety of which is hereby incorporated herein by reference. Before a user registers, the Financial Institution PKM Module 40A, 40B maintains a table or other record in storage which relates a confidential “seed” to a publicly available “serial number”. In the registration process, the user registers a particular “serial number” to instruct the Financial Institution PKM Module 40A, 40B to associate the user, serial number, and seed together. The approval process provides further evidence to the Financial Institution PKM Module 40A, 40B that it is correctly associating the specific user with the associated serial number. After registration, the user authenticates using the One-Time Password, or executes a digital signature using the one-time password (see e.g., the method of executing digital signatures with one-time passwords, described in detail in U.S. Publication No. 2005/0091492, titled “Portable Security Transaction Protocol”, which is incorporated by reference herein). The Financial institution PKM Module 40A, 40B looks up the user's registered serial number associated with the userid. Next, the Financial Institution PKM Module 40A, 40B finds the confidential “seed” associated with the serial number. Next, the Financial Institution PKM Module 40A, 40B validates the user's submitted one-time password.

In one embodiment of the invention, the credential is a machine fingerprint and signatures are created using PSTP. As used herein, the term “machine fingerprint” is intended to include, but is not limited to, a unique characterization of a particular machine (i.e., computing device) that the machine may communicate with the Financial institution PKM Module 40A, 40B. After the Financial Institution PKM Module 40A, 40B accepts the machine fingerprint for use, the Financial Institution PKM Module 40A, 4013 prohibits electronic interaction with the user unless the user connects from a machine/computer with the registered fingerprint. In a further embodiment of the invention, the user registers a plurality of machine fingerprints. After the Financial Institution PKM Module 40A, 40B accepts the plurality of machine fingerprint for use, the Financial Institution PKM Module 40A, 40B prohibits electronic interaction with the user unless the user connects from a machine with one of the registered machine fingerprints. Example elements that may contribute to a machine fingerprint include, but are not limited to, any collection or sub-collection of: machine address, software installed on a machine, version numbers of software installed on a machine, machine name, and machine hardware characteristics. This list is intended to provide example elements that may be used as the basis of the machine fingerprint, and is not meant to be an exhaustive list. One having ordinary skill will appreciate that other suitable elements may be used in connection with defining a machine fingerprint.

According to an embodiment of the present invention, with reference to FIG. 4, steps I-V are performed electronically, wherein each step may be authenticated by a credential in order to ensure that both peers agree as to the party that executes the step. Furthermore, the types of credentials used to authenticate each of the steps do not need to be the same. The credential used in the authentication of each step may be the same as the registered credential. In one embodiment of the present invention, the type of credential used in the authentication of each step may be different than the registered credential. For example, the user may authenticate step II and step III using passwords. In this example, step IV may be authenticated using a one-time password. Optional, the credential in this example may be a certificate.

Although the modules 40A and 40B are labeled and described in the present application as “Financial Institution PKM Modules” for the purposes of illustration, one having ordinary skill in the art will appreciate that the PKM modules may be operated by an entity which is not in the financial services industry. In particular, the entity/entities may be from any industry which may use interoperable credentials, such as, for example, the healthcare industry. In an embodiment of the present invention, one or more of the entities illustrated in FIG. 1 are individuals, as opposed to corporations, financial institutions, non-financial institutions, or credential providers.

Although the Corporation/User Module 20 is labeled corporation/user for the purpose of illustration, one having ordinary skill in the art will appreciate that corporation/user module might not be operated directly by a person or persons. Rather, the Corporation/User Module 20 may be an autonomous computer system.

As shown in FIG. 1, the Corporation/User Module 20, the Credential Provider 10, and/or the Financial Institution PKM Module 40A, 40B may be communicatively connected to one another according to any number of configurations wherein the optional connections are depicted with dashed lines, thereby allowing the respective entities to communicate via electronic means according to the variety of embodiments described in detail in the present application.

It is to be understood that the exemplary embodiments are merely illustrative of the invention and that many variations of the above-described embodiments may be devised by one skilled in the art without departing from the scope of the invention. It is therefore intended that all such variations be included within the scope of the following claims and their equivalents. 

What is claimed is: 1-9. (canceled)
 10. A method for securely processing an online transaction between a user and a first financial institution, the method comprising: receiving, by a first institution partner key management module, information from a validator relating to a request for a transaction on behalf of a user, the information comprising a user-signed transaction request counter-signed by the validator, a signed revocation statement, and a partner key practice statement signed by the validator; and validating, by the first institution partner key management module, the information according to a manifest of credential usage associated with the first institution and, upon successful validation, processing the requested transaction.
 11. The method of claim 10, wherein the manifest of credential usage associated with the first institution comprises a machine-readable statement including a policy of the first institution for accepting a digital signature.
 12. The method of claim 10, wherein the user-signed transaction request is signed by a user credential.
 13. The method of claim 12, wherein the user credential is registered with the first institution.
 14. The method of claim 10, wherein the user credential is interoperable and the interoperable credential is used to secure a transaction with a second institution according to a second manifest of credential usage.
 15. (canceled)
 16. The method of claim 14, wherein the second manifest of credential usage differs from the manifest of credential usage of the first institution.
 17. The method of claim 10, wherein the validator is one of the user, a corporation associated with the user, a trusted third party, and the first institution.
 18. (canceled)
 19. (canceled)
 20. The method of claim 10, wherein a plurality of other institutions respectively accept a manifest of credential usage that is the same as the first financial institution's manifest of credential usage. 21-23. (canceled)
 24. The method of claim 14, wherein the first institution and a second institution confirm that the credential is registered, thereby establishing the credential as an interoperable credential.
 25. The method of claim 13, further comprising authorizing by the first institution, the credential to represent the user with regard to an online transaction with the institution, wherein the credential is interoperable with at least one other financial institution.
 26. A system for securely processing an online transaction between a user and a first financial institution, the method comprising: a first institution partner key management module communicatively coupled over a network to a user module, the first institution partner key management module comprising: a memory configured to store a manifest of credential usage associated with the first institution; and a processor configured to: receive information from a validator relating to a request for a transaction on behalf of a user, the information comprising a user-signed transaction request counter-signed by the validator, a signed revocation statement, and a partner key practice statement signed by the validator; and validate the information according to a manifest of credential usage associated with the first financial institution and, upon successful validation, processing the requested transaction.
 27. The system of claim 26, wherein the user-signed transaction request is signed by a user credential.
 28. The system of claim 26, wherein the user credential is registered with the financial first institution.
 29. The system of claim 26, wherein the user credential is interoperable and the interoperable credential is used to secure a transaction with a second institution according to a second manifest of credential usage.
 30. The system of claim 29, wherein the second manifest of credential usage differs from the manifest of credential usage of the first institution.
 31. The system of claim 26, wherein the validator is one of the user, a corporation associated with the user, a trusted third party, and the first institution.
 32. The system of claim 30, wherein the first institution and a second institution confirm that the credential is registered, thereby establishing the credential as an interoperable credential.
 33. A computer-readable medium comprising computer executable software code tangibly embodied thereon, the code for conducting an online transaction using an established interoperable credential, the code comprising: code for receiving, by a first institution partner key management module, information from a validator relating to a request for a transaction on behalf of a user, the information comprising a user-signed transaction request counter-signed by the validator, a signed revocation statement, and a partner key practice statement signed by the validator; and code for validating, by the first institution partner key management module, the information according to a manifest of credential usage associated with the first institution and, upon successful validation, processing the requested transaction. 